-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade actions/deploy-pages v1.2.8 -> v2.0.2 #674
Conversation
Suggested commit message:
|
Looks good. No mutations were possible for these changes. |
2 similar comments
Looks good. No mutations were possible for these changes. |
Looks good. No mutations were possible for these changes. |
8eeb6b1
to
09be28d
Compare
Looks good. No mutations were possible for these changes. |
09be28d
to
cb46fc1
Compare
Looks good. No mutations were possible for these changes. |
cb46fc1
to
556dd97
Compare
Looks good. No mutations were possible for these changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested commit message:
Upgrade actions/deploy-pages v1.2.8 -> v2.0.2 (#674)
See:
- https://github.com/actions/deploy-pages/releases/tag/v2.0.2
- https://github.com/actions/deploy-pages/releases/tag/v2.0.1
- https://github.com/actions/deploy-pages/releases/tag/v2.0.0
For now, the entries are in a different order than we are used to, but I'd say for now it's fine. We will probably try to contribute something upstream that allows us to reverse this list.
Looks good. No mutations were possible for these changes. |
4e612f5
to
da6e0fb
Compare
Looks good. No mutations were possible for these changes. |
2 similar comments
Looks good. No mutations were possible for these changes. |
Looks good. No mutations were possible for these changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that the manually suggested commit message lacks reference to the 2.0.2 release :)
da6e0fb
to
68295d0
Compare
@rickie the suggested commit message should now be pruned, as it's now an upgrade starting from 1.2.8. |
Good catch @Stephan202, thanks! |
Looks good. No mutations were possible for these changes. |
1 similar comment
Looks good. No mutations were possible for these changes. |
Looks good. No mutations were possible for these changes. |
8 similar comments
Looks good. No mutations were possible for these changes. |
Looks good. No mutations were possible for these changes. |
Looks good. No mutations were possible for these changes. |
Looks good. No mutations were possible for these changes. |
Looks good. No mutations were possible for these changes. |
Looks good. No mutations were possible for these changes. |
Looks good. No mutations were possible for these changes. |
Looks good. No mutations were possible for these changes. |
Kudos, SonarCloud Quality Gate passed! |
Looks good. No mutations were possible for these changes. |
1 similar comment
Looks good. No mutations were possible for these changes. |
This PR contains the following updates:
v1.2.8
->v2.0.2
Release Notes
actions/deploy-pages
v2.0.2
Compare Source
Changelog
See details of all code changes since previous release.
v2.0.1
Compare Source
Changelog
🚀 Features
🧰 Maintenance
See details of all code changes since previous release.
v2.0.0
Compare Source
Changelog
See details of all code changes since previous release.